Automated billing and distribution platform for application providers

ABSTRACT

Integrating a network-enabled application with a platform having a plurality of users and a plurality of communication channels with a respective plurality of wireless network carriers, including receiving a request from a third-party provider to integrate a network-enabled application with the platform, receiving a set of registration data corresponding to the network-enabled application from the third-party provider, the set of registration data including a link to an application location for accessing the network-enabled application, receiving a set of pricing structure data corresponding to the network-enabled application from the third-party provider, updating a system database in the platform to include the set of registration data and the pricing structure data corresponding to the network-enabled application, and enabling the network-enabled application to be accessible to the plurality of users via a networked interface operated by the platform.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application claims the benefit of priority as a Continuationunder 35 U.S.C. §120 of U.S. patent application Ser. No. 12/620,507entitled “AUTOMATED BILLING AND DISTRIBUTION PLATFORM FOR APPLICATIONPROVIDERS,” which in turn claims the benefit of priority as a Divisionunder 35 U.S.C. §120 to U.S. patent application Ser. No. 11/516,921entitled “AUTOMATED BILLING AND DISTRIBUTION PLATFORM FOR APPLICATIONPROVIDERS,” filed on Sep. 6, 2006, which in turn claims the benefit ofpriority under 35 U.S.C. §119 from U.S. Provisional Patent ApplicationSer. No. 60/714,978 entitled “AUTOMATED MOBILE PHONE BILLING ANDDISTRIBUTION PLATFORM FOR APPLICATION PROVIDERS,” filed on Sep. 7, 2005,all of which are incorporated herein by reference in their entirety asif set forth in full.

FIELD OF THE INVENTION

The present invention relates to an automated distribution and billingplatform for networked applications, and, more particularly, relates toa micro-transaction billing platform through which transactions areconducted for the access and use of networked applications by mobilephone users.

BACKGROUND

While credit card use and automatic credit card billing is a common wayto conduct business transactions in many countries, they are notnecessarily the best way in some situations. In particular, there aremany users of the internet that do not have access to a credit card ordo not want to use their credit card for an internet based transactionout of security concerns. Many such users most likely have a mobilephone or mobile device, and it would be easy and efficient to have amechanism for billing the user for transactions through the user'spre-existing account with the wireless network carrier associated withthe user's mobile phone number. In addition, the use of a credit card iseconomically viable only if the transaction amount, or a volume of suchtransactions, exceeds a particular amount that depends on the underlyingefficiency of the billing and collecting system implemented by themerchant and by the credit card provider. Currently, wireless networkcarriers routinely bill users for small transactional amounts, such as aone minute call, or portion thereof, and are able to bill and collectfor these small transactions while making a profit. These smalltransactions are referred to as micro-transactions and, in terms of U.S.currency, can be as small as a few pennies, although larger transactionsoccur as well.

Retailers or vendors, such as internet commercial websites that provideproducts or services, may desire to provide their respective content orservices to mobile phone users via the internet or directly through theuser's mobile phone, and bill the user for such content or services asmicro-transactions. For example, a third-party internet website mayprovide users with access to frequent summaries of sports game scoresand news or other premium content, for a fixed price per month.Currently, a retailer or vendor will find it very difficult andinefficient to bill and collect for such a micro-transaction because theretailer/vendor would need to negotiate and enter into a contractualrelationship with the user's wireless network carrier in order to billthe mobile phone user subscribed to that carrier. The process is furthercomplicated by the fact that the universe of customers with mobilephones use different wireless network carriers. Accordingly, theretailer/vendor would need to enter into contractual relationships witheach of the many different wireless network carriers in order to be ableto provide a mobile phone based micro-transaction billing option to thedesired global market of mobile phone users. A retailer or vendor cantry to use billing mechanisms other than wireless network carriers, suchas prepaid card services, web-based payment services, bank account andcredit card billing services, and other such external billing mechanismsto support customer transactions. However, in such examples, the sameproblem still exists for the vendor/retailer because they would stillneed to have pre-existing relationships with all of the various externalbilling mechanisms that their various customers wish to use for paymentof transactions. In addition, a retailer/vendor often finds it difficultto efficiently market their product/service to the users of each of themany different wireless network carriers.

Thus, there exists a need for retailers and vendors with networkedapplications to have the ability to easily market and conducttransactions, many of which may be micro-transactions, with a globalmarket of mobile phone users, where the transactions are easily billablethrough a single intermediate billing platform which can effectuate atransaction through a wide variety of external billing mechanisms onbehalf of the retailer/vendor, thereby eliminating the need for theretailer/vendor to establish an individual contractual relationship witheach of the external billing mechanisms, while providing theretailer/vendor with efficient access to the global market.

SUMMARY

The present invention solves the foregoing problems by providing asystem and method for retailers and vendors with networked applicationsto efficiently integrate their respective networked applications withina global market of mobile phone users, wherein the retailers and vendorscan easily conduct transactions with the users, many of which may bemicro-transactions, and the transactions are easily billable through asingle intermediate billing platform which can effectuate a transactionthrough a wide variety of external billing mechanisms on behalf of theretailer/vendor. In this manner, there is no need for theretailer/vendor to establish an individual contractual relationship witheach of the external billing mechanisms, and the retailer/vendor isinstantly provided with efficient access to a global market of users.

In one aspect, the present invention relates to a method and platformfor integrating a network-enabled application with a platform having aplurality of users and a plurality of communication channels with arespective plurality of wireless network carriers, including receiving arequest from a third-party provider to integrate a network-enabledapplication with the platform, receiving a set of registration datacorresponding to the network-enabled application from the third-partyprovider, the set of registration data including a link to anapplication location for accessing the network-enabled application,receiving a set of pricing structure data corresponding to thenetwork-enabled application from the third-party provider, updating asystem database in the platform to include the set of registration dataand the pricing structure data corresponding to the network-enabledapplication, and enabling the network-enabled application to beaccessible to the plurality of users via a networked interface operatedby the platform.

In another aspect, the present invention relates to a method andplatform for billing a user for the use of a network-enabled applicationthat is integrated with a platform having a plurality of users and aplurality of communication channels with a respective plurality ofwireless network carriers. The invention includes detecting, in theplatform, a billing event generated by the network-enabled application,the billing event containing an identification code corresponding to theuser, validating, in the platform, the billing event generated by thenetwork-enabled application by determining if the billing event is inaccordance with a predetermined pricing structure corresponding to thenetwork-enabled application, sending, in the case that the billing eventis determined to be valid in the billing validation step, a billingmessage from the platform to an external billing mechanism (such as oneof the wireless network carriers that corresponds to the user), thebilling message containing a billing amount which the external billingmechanism is to bill the user, and discarding, in the case that thebilling event is determined to be invalid in the billing validationstep, the billing event from the platform.

Other aspects include providing an automatic cut-off feature whichpermits a particular application to be disabled from operation throughthe platform if a threshold number of user complaints have been receivedabout the application. In this manner, the users of the platform havecontrol through the platform to disable a disreputable or improperapplication. Also, in another aspect, the platform automaticallyevaluates a billable event from an application by comparing it to thespecified terms and conditions of the corresponding pricing structure,and then will discard the billable event if it is in violation of theterms and conditions. In this manner, the platform provides automaticregulation to prevent improper activity or billing by an applicationthat is accessed through the platform. Also, other billing mechanismscan be used rather than sending a billing message to the wirelessnetwork carrier of the user, such as the use of prepaid card services',web-based payment services, bank account and credit card billingservices, and other such external billing mechanisms to support customertransactions.

Accordingly, it is unnecessary for the application provider to havecontractual agreements with any of the wireless network carriers,because the billing is automatically performed by the platform throughthe wireless network carriers on behalf of the application providers.The platform requires the application providers to use a standardizedpricing structure in order to provide a consistent experience for usersof the applications that are accessed through the platform. Theinvention provides application providers with a simple, efficient andautomatic way to register and present their applications to a largecommunity of users through the platform.

It is understood that other embodiments of the present invention willbecome readily apparent to those skilled in the art from the followingdetailed description, wherein is shown and described only variousembodiments of the invention by way of illustration. As will berealized, the invention is capable of other and different embodimentsand its several details are capable of modification in various otherrespects, all without departing from the spirit and scope of the presentinvention. Accordingly, the drawings and detailed description are to beregarded as illustrative in nature and not as restrictive.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a computer system with which the presentinvention may be practiced, according to one embodiment of theinvention;

FIG. 2 is a block diagram of a wireless network environment in which theinvention may be practiced, according to one embodiment of theinvention;

FIG. 3 is a block diagram providing a detailed view of the platformshown in FIG. 2;

FIG. 4 is a flowchart for explaining the integration of anetwork-enabled application, according to one embodiment of theinvention;

FIG. 5 is a block diagram depicting a webpage for developing anetwork-enabled application, according to one embodiment of theinvention;

FIG. 6 is a block diagram depicting a webpage for explaining theintegration of a network-enabled application, according to oneembodiment of the invention;

FIG. 7 is a block diagram depicting a webpage for entering informationrelated to a network-enabled application, according to one embodiment ofthe invention;

FIG. 8A is a block diagram depicting a first portion of a webpage forentering information related to a network-enabled application, accordingto one embodiment of the invention;

FIG. 8B is a block diagram depicting a second portion of a webpage forentering information related to a network-enabled application, accordingto one embodiment of the invention;

FIG. 8C is a block diagram depicting a summary display of informationand pricing related to a network-enabled application, according to oneembodiment of the invention;

FIG. 9 is a block diagram depicting an application, according to oneembodiment of the invention;

FIG. 10 is a block diagram depicting a profile webpage, according to oneembodiment of the invention;

FIG. 11 is a flowchart for explaining the subscription of a user to anetwork-enabled application, according to one embodiment of theinvention;

FIG. 12 is a flowchart for explaining the operation of a network-enabledapplication, according to one embodiment of the invention;

FIG. 13 is a block diagram for explaining the operation of anetwork-enabled application, according to one embodiment of theinvention;

FIG. 14 is a block diagram for explaining the operation of anetwork-enabled application, according to another embodiment of theinvention;

FIG. 15 is a flowchart for explaining the control of a network-enabledapplication based on user complaints, according to one embodiment of theinvention; and

FIG. 16 is a flowchart for explaining the control of a network-enabledapplication based on a predetermined pricing structure, according to oneembodiment of the invention.

DETAILED DESCRIPTION

At least portions of the invention can be implemented on a networkedcomputing system via a network, such as the Internet. An example of sucha networked system is described in FIG. 1. The description of thenetwork and computer-based platforms that .follows is exemplary.However, it should be clearly understood that the present invention maybe practiced without the specific details described herein. Well knownstructures and devices are shown in block diagram form in order to avoidunnecessarily obscuring the present invention.

FIG. 1 is a block diagram that illustrates a computer system 100 uponwhich an embodiment of the invention may be implemented. Computer system100 includes a bus 102 or other communication mechanism forcommunicating information, and a processor 104 coupled with bus 102 forprocessing information. Computer system 100 also includes a main memory106, such as a random access memory (RAM) or other dynamic storagedevice, coupled to bus 102 for storing information and instructions tobe executed by processor 104. Main memory 106 also may be used forstoring temporary variables or other intermediate information duringexecution of instructions to be executed by processor 104. Computersystem 100 further includes a read only memory (ROM) 108 or other staticstorage device coupled to bus 102 for storing static information andinstructions for processor 104. A storage device 110, such as a magneticdisk or optical disk, is provided and coupled to bus 102 for storinginformation and instructions.

Computer system 100 may be coupled via bus 102 to a display 112, such asa cathode ray tube (CRT), for displaying information to a computer user.An input device 114, including alphanumeric and other keys, is coupledto bus 102 for communicating information and command selections toprocessor 104. Another type of user input device is cursor control 116,such as a mouse, a trackball, or cursor direction keys for communicatingdirection information and command selections to processor 104 and forcontrolling cursor movement on display 112. This input device typicallyhas two degrees of freedom in two axes, a first axis (e.g., x) and asecond axis (e.g., y), that allows the device to specify positions in aplane.

Computer system 100 operates in response to processor 104 executing oneor more sequences of one or more instructions contained in main memory106. Such instructions may be read into main memory 106 from anothercomputer-readable medium, such as storage device 110. Execution of thesequences of instructions contained in main memory 106 causes processor104 to perform the process steps described herein. In alternativeembodiments, hard-wired circuitry may be used in place of or incombination with software instructions to implement the invention. Thus,embodiments of the invention are not limited to any specific combinationof hardware circuitry and software.

The term “compute!-readable medium” as used herein refers to any mediumthat participates in providing instructions to processor 104 forexecution. Such a medium may take many forms, including but not limitedto, non-volatile media, volatile media, and transmission media.Non-volatile media includes, for example, optical or magnetic disks,such as storage device 110. Volatile media includes dynamic memory, suchas main memory 106. Transmission media includes coaxial cables, copperwire and fiber optics, including the wires that comprise bus 102.Transmission media can also take the form of acoustic or light waves,such as those generated during radio-wave and infra-red datacommunications.

Common forms of computer-readable media include, for example, a floppydisk, a flexible disk, hard disk, magnetic tape, or any other magneticmedium, a CD-ROM, any other optical medium, punchcards, papertape, anyother physical medium with patterns of holes, a RAM, a PROM, and EPROM,a FLASH-EPROM, any other memory chip or cartridge, a carrier wave asdescribed hereinafter, or any other medium from which a computer canread.

Various forms of computer readable media may be involved in carrying oneor more sequences of one or more instructions to processor 104 forexecution. For example, the instructions may initially be carried on amagnetic disk of a remote computer. The remote computer can load theinstructions into its dynamic memory and send the instructions over atelephone line using a modem. A modem local to computer system 100 canreceive the data on the telephone line and use an infra-red transmitterto convert the data to an infra-red signal. An infra-red detector canreceive the data carried in the infra-red signal and appropriatecircuitry can place the data on bus 102. Bus 102 carries the data tomain memory 106, from which processor 104 retrieves and executes theinstructions. The instructions received by main memory 106 mayoptionally be stored on storage device 110 either before or afterexecution by processor 104.

Computer system 100 also includes a communication interface 118 coupledto bus 102. Communication interface 118 provides a two-way datacommunication coupling to a network link 120 that is connected to alocal network 122. For example, communication interface 118 may be anintegrated services digital network (ISDN) card or a modem to provide adata communication connection to a corresponding type of telephone line.As another example, communication interface 118 may be a local areanetwork (LAN) card to provide a data communication connection to acompatible LAN. Wireless links may also be implemented. In any suchimplementation, communication interface 118 sends and receiveselectrical, electromagnetic or optical signals that carry digital datastreams representing various types of information.

Network link 120 typically provides data communication through one ormore networks to other data devices. For example, network link 120 mayprovide a connection through local network 122 to a host computer 124 orto data equipment operated by an Internet Service Provider (ISP) 126.ISP 126 in turn provides data communication services through the worldwide packet data communication network now commonly referred to as the“Internet” 128. Local network 122 and Internet 128 both use electrical,electromagnetic or optical signals that carry digital data streams. Thesignals through the various networks and the signals on network link 120and through communication interface 118, which carry the digital data toand from computer system 100, are exemplary forms of carrier wavestransporting the information.

Computer system 100 can send messages and receive data, includingprogram code, through the network(s), network link 120 and communicationinterface 118. In the Internet example, a server 130 might transmit arequested code for an application program through Internet 128, ISP 126,local network 122 and communication interface 118. The received code maybe executed by processor 104 as it is received, and/or stored in storagedevice 110, or other non-volatile storage for later execution. In thismanner, computer system 100 may obtain application code in the form of acarrier wave. Of course, other types and forms a computing systems maybe used to practice the invention.

FIG. 2 depicts a block diagram of a computer-based platform 202 in whichthe invention is practiced, according to one embodiment. Users212,214,216 can connect to platform 202 via a network or similarcommunications channel 210. Via the connection, a user (e.g., 212) maycreate a profile page or “home page” that they can personalize. Thisprofile page can include various files and content that the user wantsto share with other members of platform 202.

The profile page may include a hierarchy of pages, some of which are forpublic view and some of which have restrictions on viewing (private).For example, platform 202 can be logically organized into neighborhoodssuch as “friends”, “family”, “workplace”, “dog owners”, etc. Users 212,214, 216 can belong to these different neighborhoods and share differentpages with the members of the different neighborhoods.

As seen in FIG. 2, platform 202 connects with various wireless networkcarrier systems 204, 206, 208, each of which has an associated communityof wireless network subscribers, 224, 226 and 228. In this regard, eachof wireless network carrier systems 204, 206, 208 is a carrier networkand system for supporting mobile devices including mobile phones andother mobile devices such as personal device assistants (pda). Eachwireless network carrier system is generally a wireless networkprovider, which can be cellular, PCS, or other wireless spectrum. Users212, 214, 216 of the platform 202 are also subscribers of one or more ofthe various wireless network carriers, which support the mobile phones,or other mobile devices, of users 212, 214, 216. In this way, users 212,214, 216 of platform 202 can access other users' profile pages throughthe computer-based platform of platform 202, and they can also accessthe subscribers 224, 226 and 228 of the various wireless network carriersystems 204, 206, and 208 who also belong to platform 202.

A significant benefit of the architecture depicted in FIG. 2, is thatthe platform 202 has pre-existing contractual relationships with thevarious wireless network carrier systems 204, 206, 208 for accessingsubscribers through each carrier systems and for billing subscribersthrough their respective carrier system for content and servicespurchased by the subscriber through platform 202. As is known in theart, the wireless network carrier systems 204, 206, 208 provide textmessaging and also premium text message functionality. Such messages aresent via the wireless network carrier's infrastructure to its mobilesubscribers and, internal to the wireless network carrier'sinfrastructure, the sending of such a message generates a billing eventaccording to a particular tariff rate, which then is added to thesubscriber's bill from that wireless network carrier. In another billingmode, the subscriber is pre-paid by a certain pre-paid amount with thewireless network carrier, and the sending of such a message in thisbilling mode generates subtracts an amount corresponding to a particulartariff rate from the pre-paid amount of the subscriber's account.

When platform 202 sends a message via a wireless network carrier system(e.g., 204), it is billing the subscriber-recipient of the message usingthe existing billing system of that wireless network carrier. Thebilling event is often a micro-transaction of a small monetary amount(e.g., less than one dollar). Thus, a user (e.g., 212) of the platformmay purchase a service or content within platform 202 and be billed forthose transactions through that user's wireless network carrier serviceaccount. The present invention provides for such micro-transactionbilling support through platform 202 for a transaction between a user(e.g., 212) and an application provider. In this manner, an applicationprovider need only communicate with platform 202 to conduct transactionswith users, and does not require any affiliation or agreement with thevarious wireless network carrier systems of the users. As mentionedabove, other billing mechanisms can be used by the platform rather thanbilling the user through the wireless network carrier of the user, suchas prepaid card services, web-based payment services, bank account andcredit card billing services, and other such external billing mechanismsto support customer transactions.

FIG. 3 depicts a more detailed view of the high-level system view ofFIG. 2. In particular, the system of FIG. 3 can be used to conductmicro-transactions in which a wireless network carrier's billing systemis used by the platform 202 to automatically bill the user for eachmicro-transaction with a vendor/retailer through an application, withoutthe need for a negotiation or contract between the vendor and thewireless network carrier. One example of this feature is that ofinformation distribution where application developers can offerinformation, such as stock quotes, to the users of the platform 202through applications while taking advantage of the billing arrangementsalready in place between the platform 202 and the wireless networkcarriers 204, 206, 208. Of course, an application may provide any othertype of content or service to users of platform 202, such asinformation, communication, games, etc.

Some of the sub-components of the platform 202 are a developer'sinterface 306, the user area 304 where the content, community andcommerce functions are handled for the users, and a multimedia messagingsystem (MMS) 302. The details of these different subcomponents are morefully explained throughout the remainder of this detailed description.

As noted earlier, users 212, 214 and 216 can visit the user area 304 toparticipate in an on-line community that includes various content andcommerce opportunities. This is typically accomplished via a user's webbrowser which may be run from a laptop or desktop computer, or, in thealternative, even on the user's mobile device such as a PDA, mobilephone, or other mobile device. Thus, the user area 304 includes a webserver that communicates with users 212, 214, 216 and includes a datastore of user information and other content, and also includes databasesand records. With these resources, the platform 202 is able to presentto a user 212 a profile page (“home page”) that reflects content andinformation associated with, and desired by, that particular user. Thiscontent and information is not maintained on the local computer beingused by the user 212 but, rather, is maintained and managed by thecomputer systems within the user area 304.

Although not explicitly depicted in FIG. 3, one of ordinary skill willrecognize that there are numerous functionally equivalent techniques tocreate, manage, store and serve user information, user profiles, usercontent, software tools and other resources within the user area 304.Included in these techniques are methods to ensure security, dataintegrity, data availability and quality of service metrics. In thepresent exemplary embodiment, user 212 is illustrated connecting to userarea 304 with a desktop computer, user 214 is illustrated as connectingto user area 304 via a wireless connection (dotted line) from a notebookcomputer, and user 216 is illustrated as connecting to user area 304 viaa wireless connection (dotted line) from a mobile device. As will beapparent to one of ordinary skill in the art, however, the scope of thepresent invention is not limited to these particular devices, but ratherencompasses any network-enabled device using any network connectiontechnique to connect to a user area.

The multimedia messaging system 302 includes applications for connectingwith and communicating with the multiple different wireless networkcarriers 204, 206, 208 that have been partnered with platform 202. TheMMS 302 is configured to generate message requests in the appropriateformat for each of the wireless network carriers 204, 206, 208 includingtariff information that determines the amount for which the recipient ofthe message will be charged. Upon receipt of the message request, thewireless network carriers 204, 206, 208 will use the information in therequest to generate an appropriate message to the intendedrecipient/subscriber of the wireless network carrier and then bill therecipient/subscriber's wireless network service account for thespecified amount.

The MMS 302 communicates with the user area 304, such that users of theplatform 202 can advantageously use the pre-existing connectivity of theMMS 302 with the wireless network carriers in order to send messages tosubscribers of any of the wireless network carriers 204, 206, 208. Themessages may be SMS messages, MMS messages, or other message formatsthat are subsequently developed. Some of these messages may have zerotariff and, therefore do not generate a bill (other than the underlyingcharges implemented by the wireless network carrier) and others may havenon-zero tariffs resulting in a billing event for the recipient user.

The developer's interface 306 provides a link between applicationdevelopers/providers 308, 310 and the platform 202. In particular, usingan interface 312 (described in more detail herein), an applicationprovider 308, 310 may offer services and products to users 212, 214,216. Advantageously for the application provider 308, 310, thedeveloper's interface 306 also provides automatic and instantconnectivity to the wireless network carriers 204,206,208 via MMS 302.Accordingly, the application provider 308, 310 can interact with allusers of the platform 202 through which billable transactions with users212, 214, 216 are automatically billed via the billing systems of thewireless network carriers 204, 206, 208, on behalf of the applicationprovider. Furthermore, and importantly, this capability is available tothe application provider 308, 310 without requiring the applicationprovider 308, 310 to negotiate or contract with any wireless networkcarrier for billing arrangements, or to worry about how to communicatewith a wireless network carrier's systems and resources. The applicationprovider seamlessly takes advantage of the unified set of connectivityand billing arrangements that exist between the platform 202 and thewireless network carriers 204, 206, 208. Thus, in addition to thecontractual arrangements and affiliations the platform 202 has in placewith different wireless network carriers 204, 206, 208, the underlyingtechnical and communications infrastructure is also in place tocommunicate with and interoperate with each of the different wirelessnetwork carriers 204,206,208. As a result, application providers(vendors) and other users of the platform may interface with and operatewith any of the users of a variety of different wireless networkcarriers without difficulty.

While developer's interface 306 has been described as running on acomputer-based platform, the scope of the present invention is notlimited to such an arrangement. Rather, as will be apparent to one ofskill in the art, the present invention has application to anyone of anumber of arrangements in which a developer's interface provides a linkbetween application developers and the platform 202.

While the terms “application provider” and “user” have been used todistinguish those who provide content from those who enjoy it, it willbe easily understood by one of skill in the art that a single person maybe both a user and an application provider. Indeed, as the presentinvention renders the registration of an application so simple, manyusers of platform 202 will be motivated to become application developersas well, further increasing the amount and variety of content availablevia platform 202.

While some applications that are available to users 212, 214, 216 may behosted in the user area 304, the developer's interface 306, or elsewherein the platform 202, it is often the case that the applicationdeveloper/provider 308, 310 will host their own application at their ownremote location. Accordingly, in the description that follows, even if aremotely-hosted application is being discussed in a specific example,one of ordinary skill will readily appreciate that an application beinghosted differently is also expressly contemplated.

FIG. 4 depicts a flowchart of an exemplary method for integratingapplications with the platform architecture of FIG. 2. In a first step402, an application developer identifies a marketplace need that is notbeing fulfilled. In other words, the application developer believes thatthere is a service or product that they can provide to networked usersthat will be profitable to the developer. The variety of different typesof services, content and products that can be offered to users via anapplication is limited only by the imagination of the differentapplication developers.

The term “pod service” or “application” is used in the followingdescription as a label for an application offered through platform 202,which provides a service or product. This label is used merely forconvenience and is not intend to limit or restrict the types, varietyand capabilities of potential applications in any way. As used herein,the term “pod” refers both to the underlying information related to theapplication and to the graphical rendering of the application on auser's profile page within the platform 202.

Once the marketplace is identified, the developer commences developmentof their application in step 404. The underlying application logic is upto the developer and can utilize any of the widely known programmingenvironments and techniques available to one of ordinary skill in thisarea. However, the application will be offered within the platform 202along with a variety of other applications. Accordingly, standardizingthe look and feel of the application and information about theapplication will aid the users 212, 214, 216 and make their userexperience more enjoyable.

Once an application has been developed (and most likely tested andverified) by a developer, the developer registers, in step 406, theapplication with the platform 202 through developer's interface 306.Registering the application, which is described in more detail laterwith reference to a number of screenshots, allows the applicationdeveloper to inform the developer's interface 306 that a new applicationis available for integration with and subsequent access through platform202.

Once an application is registered, the developer's interface 306updates, in step 408, system databases and directories (provided instorage 311) for the new application and its associated information. Inthe above description of FIG. 4, it is evident that the applicationdeveloper communicates with the platform 202 for a number of differentreasons. One of ordinary skill will recognize that these variouscommunications between the application developer and the platform 202can occur via any of a variety of functionally equivalent means. Forexample, both wired and wireless communication methods for thesecommunications are explicitly contemplated within the scope of thepresent invention.

FIG. 5 is a screenshot of an exemplary screen 500 that applicationdevelopers may be presented with via the Internet by platform 202 toassist in registering a new application. From this screen 500, theapplication developer can navigate to a screen that provides moretechnical information such as the one shown in FIG. 6. This screen 600of FIG. 6 illustrates to the developer how the application takesadvantage of the existing payment mechanism of platform 202 when used byan end user.

FIG. 7 is a screenshot of an exemplary application registration screen700 according to one embodiment of the present invention. Because theapplication is most likely hosted remotely, an input window 702 allowsthe application developer to provide the URL of where the application islocated. When a user ultimately accesses and uses the pod through theplatform 202, this URL is the location from where the content for theapplication is retrieved. For example, if the application was developedto display pictures for a dating service, this URL would point to codethat when executed could detect user input events and result in thedisplay of appropriate images.

The pod developer can utilize the field input boxes 704 to specifydifferent fields that can capture input when a user first accesses apod. For example, if an application is developed to provide stockquotes, then these fields could be defined to accept stock symbols. Whenthe user views the pod within their profile page, these fields can befilled in with appropriate stock symbols, for example. Then, when theuser then selects a “submit” button on the pod, this information is sentto the application developer's computing device which returns theappropriate information.

As is well known to HTML and HTTP developers, based on the informationthat is filled in the field windows 704, a particular query string willbe appended to a request received from a user's from submission. To aida developer in registering a pod, this query string is automaticallygenerated and displayed for the pod developer in region 706 of theexemplary screen. To give the pod developer a quick view of how the podwill be rendered, a button 708 is provided to illustrate the pod. Withthis information, the developer may choose to revise their design.

Once this initial information is collected, the developer's interface306 collects additional information that is associated with the pod.FIGS. 8A and 8B depict the first half screen 800 and the second halfscreen 801 of a registration webpage for inputting registration, inwhich a number of input fields 802-830 are provided for the poddeveloper to fill in while registering their application. Many of thesefields are self-explanatory; however, some warrant amore detaileddiscussion. In particular, a pricing window 816 is available for thedeveloper to select an appropriate pricing scheme, according to astandardized pricing structure. According to one embodiment of thepresent invention, pricing occurs in fixed tariff bands. For example,one band would be a $0.25 band and would be used for products orservices that the developer thinks users would purchase for around$0.25. Another band may be $1.00 and would be for higher priced itemsand still other bands can be used as well. According to thisarrangement, not all prices are available to the developer; instead, thedeveloper picks the closest band to use (e.g., the $1.00 band isselected even if market research shows users would actually pay $1.03for the service).

Additionally, the application will likely be used by people in differentcountries. Because of the vagaries of global economics, $0.25 may be toohigh of a price-point in many countries. Thus, it is more appropriate toset a price-point for each separate country from which the applicationmay be used. While it is possible for the developer's interface 306 topermit the pod developer to set such a vast number of price-points, mostdevelopers will not have the knowledge or the patience to perform such atask. Accordingly, the developer's interface 306 automatically providesa price band selection for each country based on their respective costsof living. In other words, a developer can select a price band in thecurrency that he is comfortable with and let the developer's interface306 translate that to an equivalent price band in each country.

Via the input field 818, the developer also specifies the number ofmessages and frequency that their application will send to each user.Based on their knowledge of having developed the application to performa particular service, the pod developer may, for example, know that nomore than 4 messages per day (per user) will be sent from theirapplication. This information sets the terms and conditions for billingthe user. Thus, they would fill in this field 818 accordingly. Asexplained later, the developer's interface 306 can use this informationto control message traffic within the platform 202.

The benefit of specifying the pricing information and number of messageinformation is that the terms and conditions of the application can beprovided to a user in a uniform manner. Window 820 displays, for the poddeveloper, how the application information, including pricing, terms andconditions, will be shown to a user. FIG. 8C depicts a more detailedview of this uniform pricing display 820. Much, like nutritional labelson food products provide a uniform format for presenting the nutritionalinformation, the format depicted in window 820 can be used to uniformlypresent information about applications. Thus, a user of the platformdoes not have to learn and interpret different pricing information foreach different pod developer. Instead, the uniform format 820 simplifiesunderstanding this information. The exemplary format of window 820includes a variety of information about the application. Of particularinterest to most users is the uniform manner in which the pricinginformation 870 and the message information 872 is clearly presented.One of ordinary skill will appreciate that the format of window 820 ismerely exemplary in nature and can vary in numerous ways withoutdeparting from the scope of the present invention. Accordingly, theexemplary format of window 820 is provided to illustrate that thedeveloper's interface 306 is arranged so as to provide users of theplatform 202 with uniformly formatted information from a variety ofdifferent applications so as to simplify the evaluation and comparisonof different offerings. With such a uniform pricing arrangement beingutilized, it becomes possible to monitor the behavior of pod developerswith respect to their specified pricing structure and implement controlmeasures such as limiting or restricting their activities with users ofthe platform if warranted.

Once the information of screens 8A and 8B are submitted to thedeveloper's interface 306, the application is registered with theplatform 202. According to at least one embodiment of the presentinvention, the application is evaluated by a moderator of the platform202 to ensure it is acceptable from a technical and content point ofview for the platform 202. In this scenario, the application is notregistered until the evaluation is completed satisfactorily.

Information about a registered application is stored within thedeveloper's interface 306 in such a way that when a user wants toinclude a pod on their profile page, the pod can be rendered using thestored information and interaction between the pod and user will occurbased on the stored information as well. In such a case, the dataassociated with the user will be updated to reflect that the user is nowaccessing and using the pod.

Thus, according to the previously described technique, a pod developercan automatically register a new “application (even from a remotelocation) without difficulty in such a way that the pod automaticallybecomes available to users of the platform 202 at the conclusion of theregistration process. Furthermore, from the pod developer's point ofview, the application may immediately take advantage of the access toall users of platform 202 and to the billing platform used by theplatform 202 without the need to have existing contracts in place withany of the wireless network carriers.

Once registered, the application is made accessible to the users ofplatform 202 via a networked interface operated by the platform. Forexample, according to one aspect, the network-enabled application isintegrated with platform 202 via the application interface platform.According to another aspect, a message communication channel isestablished between the network-enabled application and the messagemanagement system. According to yet another aspect, the networkedinterface is an application webpage that is operated by platform 202 andthat includes an application identifier corresponding to thenetwork-enabled application. According to yet another aspect, thenetworked interface is an application webpage that can be downloaded toa user's mobile device, such as a mobile phone, personal deviceassistant (pda), smartphone, handheld gaming device, Blackberry®,ultra-mobile PC (UMPC), or anyone of a number of other mobile devicesknown to those of skill in the art.

One benefit of registering applications in this manner is that onceregistered, the developer's interface 306 can prevent the terms andcondition information from being subsequently changed by the poddeveloper. Thus, a user's agreed upon price and operating parameterswhen initially subscribing to the application will not later be modified(with or without their knowledge).

The users of the platform can locate available applications in a numberof different ways. First, the platform 202 facilitates sharing ofinformation by users having common tastes. Accordingly, users frequentlyvisit other users' profile pages looking for interesting applications,content and information, particularly with neighborhoods to which theuser belongs. During this visiting of other members' home pages, a usercan discover an interesting pod and want to access it for themselves. Interms of the platform, a user “owns” their own profile page and iscalled an “owner” when at their profile page. In contrast, when a uservisits some else's profile page, they are considered a “viewer”. Withinthe platform 202, the profile pages are maintained such that the view byan owner may not always correspond to that seen by a viewer as the ownermay want some information to be private and other information to bepublic.

In another instance, a user may know a friend or colleague would want aparticular application; thus, the platform 202 allows a user to informanother user about the existence of a new application. Another way inwhich applications are located is via a directory within the platform202. For example, the developer's interface 306 registers eachapplication as the developers submit them; it is a simple extension toinclude a database update and a searchable-directory update as part ofthe registration process (see step 408 of FIG. 4).

While the exemplary embodiment discussed above has described theregistration of an application using an Internet-based webpage, thescope of the present invention is not limited to this particulararrangement. Rather, as will be apparent to one of skill in the art, anapplication may be registered by a developer by providing the requisiteinformation in anyone of a number of functionally-equivalent manners.For example, and without limitation, a developer may register a newapplication by sending an appropriately formatted text-message or emailto a server configured to parse the information therein.

For purposes of this specification, the term “application” should beunderstood to encompass not only executable program code, but ratherincludes any data by which content is provided to a user. For example,according to one aspect of the present invention, an applicationregistered by an application provider or uploaded by a user may be assimple as a multimedia file or content stream for providing music and/orvideo to a user's mobile device or computer. Alternately, an applicationmay be a plaintext or markup language file or content stream such as anHTML-formatted web log (“blog”) or an aggregated news feed (e.g., RSS orATOM). As will be apparent to one of skill in the art, the presentinvention has application to anyone of a nearly limitless number ofcontent types which may be provided over a network.

A rendering of an exemplary pod 900 is depicted in FIG. 9. The podincludes a title bar 902 with a number of icons 904-908. The main window910 of the pod is where the content 912 is displayed. This content isbased on the associated application and the stored system informationassociated with this pod. From the pod 900, a user launches an initialmessage to the associated application. In instances where theapplication provides content back to the pod 900, the window 910 isupdated. By using remote scripting capability, as is known in the art,the updating of window 910 can occur without the user manuallyrefreshing the window 910. Similar to the profile pages describedearlier, the pod 900 can be designed to provide different views ofcontent 912 to a user depending on whether the user is an “owner” or a“viewer”.

The icon 904 can be selected by a user (for example, when viewingsomeone else's pod) to add that pod to their own profile page. The icon906 can be selected to inform another user about this pod and a dragicon 908 can be used to move the pod around a user interface screen. The“information” icon 914 is useful for displaying information about thepod, including the uniform pricing information described earlier.

FIG. 10 depicts a exemplary user profile page 1000 that has arrangedthereon a plurality of applications 1002, 1004, 1006. In this manner,the pods available to a user can be displayed on their profile page. Asnoted earlier, the user can access this profile page via a number ofdifferent devices and/or networks. For example, in addition to use of atraditional web browser, a portable device such as a smart phone or PDAcan be used to access the profile page and pods. Such portable devicescan utilize traditional WAP-based or HTML-based network connectiontechniques to access the pods through a network, such as a localintranet or a wide area network such as the internet, but they may alsoutilize device-based applications with proprietary network protocolsspecifically developed to advantageously utilize the capabilitiesprovided by pods and applications. For example, according to oneembodiment of the present invention, an ad-hoc wireless network createdon-the-fly between the mobile devices of several users may be used toshare profile pages and/or pods without relying upon a web-basednetwork. In such an embodiment, one mobile user may be able to access apod hosted on the mobile device of another user. As will be apparent toone of skill in the art, the scope of the present invention is notlimited to the particular networks and/or devices described above, butrather includes any network-enabled device and any network connectiontechnique used to connect such a network-enabled device to any type ofnetwork.

FIG. 11 illustrates a flowchart of an exemplary method for a user to adda pod to their profile page. In step 1102, the pod user locates aninteresting pod via a visit to another user's profile page or through adirectory search. In evaluating the pod, the user can see the terms andconditions of the pod in the uniform presentation format describedearlier. Next, in step 1104, the user chooses to add the pod to theirprofile page; typically using a standardized feature on the pod. In step1106, a confirmation page is sent to the user to ensure they know thepricing information about the pod and to ensure they are aware of thelikelihood of their wireless network service account being billed as aresult of executing the application. Assuming the user confirms theirselection, the user area 304 updates, in step 1108, its data store 315about this user such that the records indicate the user owns this newpod on their profile page. When the user next visits their profile page,in step 1110, arid as a result of the user area 304 rendering theirprofile page on their browser, the new pod will be displayed. With thepod displayed within the profile page, it is now available for use bythe user, in step 1112.

FIGS. 12 and 13 illustrate the operation of a pod and its associatedapplication server with respect to platform 202. As known to one ofordinary skill, the pod server 1304 may be a process executing on aseparate, dedicated processor or may be included as part of the userarea 304 or the developer's interface 306. In step 1202, a userinteracts with some feature on the pod user interface 1302 to generate arequest. This request, includes the URL associated with the content ofthe pod and a query string (if any) based on the fields of the pod, andinformation input by the user. The query string can be referred to astransient parameters.

In response to the request from the pod user interface, 1302, the podserver 1304 identifies the pod developer server and the URL of thecontent and adds some additional information, in step 1204. Theaugmented request is sent to the application provider's applicationserver 1306 which responds, in step 1204, to the augmented request.

In the previously mentioned incorporated document, exemplary types ofaugmented information are described in detail. In general terms, theinformation added to the augmented request includes demographicinformation about the owner and viewer of the pod. In this way, theapplication server 1306 can respond with a first type of content if theowner and viewer are the same or respond with different content if theowner and viewer are different. One way to accomplish this distinctionis for the user area 304 to refer to users by a unique user ID number.Thus, users can be distinguished without revealing sensitive informationto a application developer such as the mobile telephone number of auser. Also, the application server 1306 can use this demographicinformation to collect statistics about its users.

Other additional information that might be added would include detailsabout the type of user interface the user has available. Because usersmay be using their mobile device, their display may not be as robust asa desktop interface. Thus, application server 1306 can control contentbased on the current graphical and bandwidth capabilities of the user.For example, the additional information can indicate whether the user isoperating in a web-based or WAP-based environment.

In response to the augmented request, the application server 1306responds with code, in step 1206, that is substantially HTML data. Thiscode is generated according to the application logic of the applicationserver 1306. In other words, it is the content that is returned to theuser who is viewing the pod. In certain embodiments of the presentinvention, the code of the response varies from conventional HTML incertain ways. For example, because this is a managed communicationsystem, non-standard HTML tags can be used and supported. Thus,non-standard tags can be used that are specific to the pod environmentthat are not applicable to generic HTML pages. For example, a pod has atitle area and a message area. Tags specifically for controlling theseareas may be used to add functionality to the pod environment describedherein. One of ordinary skill will recognize that a number of differentspecialized tags and capabilities can be offered without departing fromthe scope of the present invention.

An additional variation from HTML is that of using templates whereinformation can be provided by the pod server 1304. For example, forprivacy concerns, little identifying information is sent to theapplication server 1306. However, the pod server 1304 has access to thisinformation because it communicates with the user information stored inthe user area 304. Thus, the use of templates will allow applicationserver 1306 to take advantage of this information to personalize the podexperience. For example, the template may include a tag <!FirstName!>.When the pod server 1304 encounters this tag in the template, it knowsthat the application server 1306 intends for the pod server to insertthe first name of the user. A more detailed list of exemplary templatetags is provided in the previously mentioned incorporated document.

When the pod server 1304 receives the HTML-like reply from theapplication server 1306, the pod server manipulates the reply into aformat useful for the pod environment. For example, certain HTMLfeatures such as, for example, javascript, iframe, frame, and scriptfeatures, are removed from the reply in order to improve the security ofthe content. Secondly, the pod server 1304 can replace thepersonalizable parameters in the templates with the actual userinformation. And thirdly, the pod server 1304 can translate the contentinto other display formats, depending on the operating environment ofthe user (mobile or computer).

For example, if an application provider is well-skilled in providing WAPcode as opposed to conventional HTML code, then that provider cancontrol which code, or content, is generated based on the information itknows about the user's interface. However, if an application provider isnot skilled with, or does not support, generating content in differentformats, then the application can request (as part of the code it sendsback to the pod server 1304) that the pod server 1304 translate the codeinto a more appropriate format.

Another modification the pod server 1304 can make is that ofmanipulating the hyperlinks within the code sent by the applicationprovider. Under normal behavior, such a hyperlink would result inopening another browser window and following the link. As is known toone skilled in this area, the original hyperlinks are adjusted by thepod server 1304 so that pages rendered by following the links remainunder the control of the pod server 1304 and the user interface remainswithin the focus of the pod instead of some other browser window.

Once the pod server 1304 completes its changes to the original code instep 1208, the pod server 1304 renders the code and content to theuser's pod 1302, in step 1212.

In addition to the code that is received from the developer'sapplication server 1306, the pod server 1304 can also receiveinformation from the application server 1306 about a billing event thatshould be triggered for the particular content that the user requested.For example, the user may have requested a stock quote that will cost$1.00. When application server 1306 generates the content of the reply(e.g., when application server 1306 transmits the data corresponding tothe stock quote to the mobile device of the user), it also generates amessage that the pod user should be charged $1.00 for this transaction.One of ordinary skill will appreciate that there is wide variety ofprotocols for the pod server 1304 and the application server 1306 toexchange information related to a billable transaction. Duringoperation, therefore, the developer's application server 1306 merelyadheres to the agreed upon protocols to inform the pod server 1304 thata billable transaction has occurred.

When the pod server 1304 determines that the code from the applicationserver 1306 includes an indication that billing should occur, the podserver 1304 generates a billing event 1308, in step1210. This billingevent 1308 is forwarded to the developer's interface 306 so that billingmay occur by using the wireless network carrier's underlying billingsystems. In alternative embodiments, the billing event can be handled bydeveloper's interface 306 to achieve payment through anyone of a varietyof billing mechanisms, such as prepaid card services, web-based paymentservices, bank account and credit card billing services, and other suchexternal billing mechanisms that support customer transactions. The podserver 1304 has access to the recipient information (i.e., the pod user)and the billing rate of the application supported by application server1306. Therefore, an appropriately formatted billing message is easilygenerated.

The developer's interface 306 includes a message interface 1402 tohandle billing events from a variety of sources. Although a differentinterface could be designed for each different source of billing events,it is more efficient to use a single application programming interface(API). The use of a single API is exemplary in nature and is notintended to restrict or limit the different ways that the developer'sinterface 306 can exchange messages.

One type of billing message originates from subscription-based services.Under these circumstances, a database or other storage system maintainsa record of when to send a .message to a user on a predeterminedperiodic basis (e.g., daily, monthly, weekly, etc.). When the managementsystem for these subscription services indicate that a message is to besent, then this message is forwarded to the interface 1402 (FIG. 14) ofthe developer's interface 306 with the appropriate tariff informationincluded.

As discussed earlier, the pod server 1304 can also generate a messagebased on a discrete billable event occurring due to the user's operationof an application. In this instance the billing message 1308 isforwarded to the interface 1402.

In another circumstance, the application may operate so as to avoidsending content back through the pod server 1304 but still be designedto perform a billable event. For example, the application may be avirtual greeting card application that sends text messages to peoplebased on whether it is their birthday, anniversary, etc. and charges thepod user $0.25 for each card. Thus, the application server 1306 performsbillable activities but not via the content it sends back through thepod server 1304. Under these event-based circumstances, the applicationprovider can establish a direct connection with the interface 1402 andsend a billable message via the established interface.

Regardless of how the billable event arrives at the interface 1402, thedeveloper's interface 306 processes it such that a message is sent viathe MMS 302 through the wireless network carriers to the user of thepod. This message, the content of which may say, for example, “Thank youfor being a valued customer of xxx” will have associated with it atariff code that results in the user being billed via their wirelessnetwork service account.

Thus, a business model is established where platform 202 directs awireless network carrier to bill a user for a billing event generated bythe user's use of an application, and then the revenue from that billingis shared in an agreed-upon portion with platform 202 which, in turn,shares an agreed-upon portion of that billing with the applicationprovider. The wireless network carrier benefits from additional billabledata traffic and the application provider benefits by obtaining instantaccess to all the users of the platform as well as instant access to thewireless network carriers' billing systems in a seamless and unifiedfashion through the platform. As mentioned above, other versions of thebilling model can use other billing mechanisms rather than billing theuser through the wireless network carrier of the user, such as prepaidcard services, web-based payment services, bank account and credit cardbilling services, and other such external billing mechanisms to supportcustomer transactions.

The presence of the developer's interface 306 between the applicationprovider's application 1306 and the MMS 302 provides the benefit thatthe messaging of different users of the platform 202 can be controlledto ensure the platform 202 is more enjoyable.

Within the platform architecture, the various computer-based componentsdiscussed thus far have a vast amount of information stored and readilyaccessible. For example some of the information includes: identifyinginformation about each application, identifying information about eachuser, identifying information about which pods are associated with eachuser, information about the terms and conditions regulating theoperations of an application, and information about messages being sentvia the platform 202. With this information available, one of ordinaryskill will recognize that a number of operating parameters of theplatform 202 can be monitored and controlled.

FIG. 15 depicts a flowchart of an exemplary method for instituting acomplaint monitoring program within the platform 202, which canultimately result in automatic cut-off of access to, and billingactivities by, an application. In accordance with this flowchart, whileall the parties are using the platform 202, content and services arebeing provided by different application providers in step 1502. Withinthe profile page of a user, or alternatively at a more centrally locatedwebpage operated by platform 202, a link may be provided, in step 1504,to submit a complaint. The developer's interface 306 then collects thesecomplaints and generates, in step 1506, statistics about them. Forexample, one statistic may be to identify what percentage of users of anapplication are complaining that it fails to operate as promised,provides unsuitable material, improperly bills, or includes some otherproblem.

In step 1508, the complaint statistics are evaluated to determine if aproblem exists. Typically there would be checks and balances used toensure that a single user is not abusing the system with a flood ofcomplaints or that 100 complaints is not really a problem if the userbase is 10 million. If a problem is found to exist with a particularapplication, which can be determined if the received complaints for thatapplication exceed a predetermined threshold, then in step 1510, thedeveloper's interface turns off communication between that applicationand platform 202. Thus, the pod server of platform 202 can be informedto ignore any communications to or from that particular application.Because an application provider may supply more than one application, anembodiment is provided in which the system turns off communication withall applications from that provider, not simply the ones relating toonly the problematic application.

FIG. 16 provides a flowchart of an exemplary method for regulatingmessages such that the agreed upon terms and conditions of the operatingparameters of the pricing structure for an application are adhered to.At the time a subscriber decides to subscribe to an application, thesubscriber is shown details relating to price, message frequency,maximum messages sent to the user in any given time period, and otherterms relating to the specific application. Upon agreeing to those termsand conditions, those terms and conditions are memorialized for thatspecific subscriber within the platform, such that if the applicationprovider later changes the price or other terms of the service, such newterms will only apply to the new subscribers that enter a “contract”after the date of change. The system ensures enforcement of the originalterms and conditions that each individual subscriber was shown andagreed to during subscription to the application.

In step 1602, the developer's interface 306 receives via its interface1402 a message from an application developer's application server tosend to a user. As part of the agreed upon interface, the messagearrives from an identifiable source and specifies the recipients for themessage. A recipient can be a single user or it could be a group such as“San Diego Padre fans” which the system will expand into the individualsubscribers when delivering the message.

Thus, in step 1604, the developer's interface analyzes historicalinformation about messages sent by this application sender to thespecified recipient. In step 1606, this historical data can be comparedto the pre-defined threshold limits for the application message sender.If the message would cause the pre-determined limits to be exceeded forthat application, then the message is discarded in step 1610 therebyavoiding billing of the user. If the message is allowable, then themessage is sent to the user as normal in step 1608.

In the above description of the various aspects of the presentinvention, the specific example of an application was described indetail. This specific example was provided merely to highlight many ofthe features and aspects of the present invention but one of ordinaryskill will recognize that providers of other types of products andservices may also utilize and benefit from the platform system. Inparticular, embodiments of the present invention allow applicationvendors to charge for all types of products and/or services via theplatform's pre-existing connectivity to the various wireless networkcarrier systems. In practice, a user consummates a transaction with avendor through an application for some product or service and, in theprocess, provides to the vendor a means of identifying that user withinthe platform. The vendor, in turn, will communicate with the platform(e.g., via the Mobile Global Platform) to initiate a billing event thatidentifies the purchaser and the transaction amount. As explained above,this billing event will result in the platform triggering the user'swireless network subscriber account to bill the user accordingly for thetransaction amount. In this way, the mobile phone account (although thisinformation is not necessarily revealed to the vendor) acts as a virtualwallet allowing the purchaser to easily pay for a variety of differenttypes of transactions through the use of applications. In otherembodiments, as mentioned above, other billing mechanisms can be used bythe platform rather than billing the user through the wireless networkcarrier of the user, such as prepaid card services, web-based paymentservices, bank account and credit card billing services, and other suchexternal billing mechanisms to support customer transactions.

The previous description is provided to enable any person skilled in theart to practice the various embodiments described herein. Variousmodifications to these embodiments will be readily apparent to thoseskilled in the art, and generic principles defined herein may be appliedto other embodiments. Thus, the claims are not intended to be limited tothe embodiments shown and described herein, but are to be accorded thefull scope consistent with the language of the claims, wherein referenceto an element in the singular is not intended to mean “one and only one”unless specifically stated, but rather “one or more”. All structural andfunctional equivalents to the elements of the various embodimentsdescribed throughout this disclosure that are known or later come to beknown to those of ordinary skill in the art are expressly incorporatedherein by reference and intended to be encompassed by the claims.Moreover, nothing disclosed herein is intended to be dedicated to thepublic regardless of whether such disclosure is explicitly recited inthe claims.

1. A method for integrating a network-enabled application with aplatform that hosts a social networking site having a plurality of usersand that includes a plurality of communication channels forcommunicating with a respective plurality of wireless carriers, themethod comprising: a web page establishment step of establishing, on thesocial networking site, a user profile web page associated with each ofthe plurality of users; a application access step of making a pluralityof network-enabled applications available, in the social networkingsite, to the plurality of users via an area on the social networkingsite and allowing each of the plurality of users the ability to placeone of the plurality of network-enabled application on their web pageand to access or use the network-enabled application on the web-page; arequest receipt step of receiving, at the platform, a request from athird-party provider to integrate a network-enabled application to beincluded in the plurality of network-enabled applications with thesocial networking site; a registration data receipt step of receiving,at the platform, a set of registration data corresponding to thenetwork-enabled application from the third-party provider, the set ofregistration data including a link to an application location to enablethe plurality of users to access the network-enabled application; apricing structure data receipt step of receiving, at the platform, a setof pricing structure data corresponding to the network-enabledapplication from the third-party provider; a database update step ofupdating a system database in the platform to include the set ofregistration data corresponding to the network-enabled application andto include the pricing structure data corresponding to thenetwork-enabled application; and an enablement step of enabling thenetwork-enabled application to be accessible to the plurality of usersvia a networked interface operated by the platform.